The outbound EDI process has the following states in N4:
Select: N4 selects the events, for a single operator or multiple operators that occurred between the last extract time and the current date and time. In addition, N4 creates an EDI interchange but does not create the EDI segments yet.
Extract: N4 creates the EDI transactions (in the XML format) for all the events found, and then applies EDI filters (on page 1) to the transactions.
For BAPLIE EDI messages only, to process the extract faster N4 combines the select process with the extract process and does not create EDI transactions.
Mapping: N4 translates the EDI transactions into EDI segments using the mapping file. For more information on mapping files, see EDI Message Map form (on page 1).
Unload: N4 splits the EDI segments using the delimiter specified for the EDI session and write the segments to the Segments table for an EDI interchange. N4 writes the EDI file from the EDI interchange and places the file in the local EDI mailbox specified for the EDI session.
Send: N4 sends the EDI file to the associated EDI trading partner through FTP, SFTP, or email. For more information on defining mailboxes for EDI trading partners, see EDI Trading Partner form (on page 1).
If you have configured an EDI job schedule, the Scheduler Task (OutboundSession or Communication Manager) sweeps the outbound local EDI mailboxes and sends each EDI file found to the associated EDI trading partner.
After the Unit Model Refactor, N4 no longer retires a unit if it is attached to another unit. For example, if you bundle two or more flat racks or mount a container on a chassis, N4 does not retire the bundled units or the chassis unit.
The Activity and Stowplan EDI Extracts have been modified to ensure that each Primary unit is extracted as a separate transaction (as before) and any attached equipment, such as a Payload, Carriage, or Accessory units are extracted under the AttachedEquipment section of the transaction (as before).